Vehicle occupant emergency system

ABSTRACT

A system may include a user interface, a transmitter, a processor, and a memory having a program communicatively connected to the processor. The processor may be configured to receive a body sensor output associated with an occupant of a vehicle, receive a vehicle sensor output associated with the vehicle, compare the body and vehicle sensor outputs with a threshold, prompt for a confirmation associated with at least one of the body and vehicle sensor outputs, determine an issue type based on at least one of the body and vehicle sensor outputs, and send a notification including the issue type.

BACKGROUND

Traditional vehicles, such as autonomous vehicles, may include sensorsfocused on an external environment of the vehicle, for example, tooperate the vehicle along a road while avoiding obstacles. Traditionalvehicles may also include sensors focused on an internal environment ofthe vehicle, such as an air temperature inside the vehicle, but thesesensors have no ability to measure and detect medical issues associatedwith body parameters, such as a body temperature, of occupants in thevehicle. Consequently, traditional vehicles lack the ability to respondto medical issues of one or more occupants of the vehicle. Further,these traditional vehicles lack the ability to communicate medicalissues with nearby vehicles as well as emergency vehicles, facilities,and call centers. Additionally, typical vehicles lack the ability toautomatically communicate with and route occupants to facilities thatare capable of treating the medical issues. Accordingly, there is a needfor a system configured to detect, communicate, and respond to medicalissues, e.g., using one or more sensors associated with the bodyparameters of one or more occupants of the vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary system of the present disclosure;

FIG. 2 illustrates an exemplary diagnostic process;

FIG. 3 illustrates an exemplary routing process; and

FIG. 4 illustrates an exemplary adaptive correction process.

DETAILED DESCRIPTION

A system may include a user interface, a transceiver, a processor, and amemory having a program communicatively connected to the processor. Theprocessor may be configured to receive a body sensor output associatedwith an occupant of a vehicle, receive a vehicle sensor outputassociated with the vehicle, compare the body and vehicle sensor outputswith a threshold, prompt for a confirmation associated with at least oneof the body and vehicle sensor outputs, determine an issue type based onat least one of the body and vehicle sensor outputs, and send anotification including the issue type.

The processor may further be configured to receive a facility listhaving a medical capability and a facility location for a plurality offacilities, select one of the plurality of facilities from the facilitylist based in part on a comparison between the medical issue and themedical capability of at least a portion of the plurality of facilities,and determine a route to the selected facility. The processor mayfurther be configured to instruct a vehicle computer of the vehicle todrive the vehicle to the selected facility based on the determinedroute.

FIG. 1 illustrates an exemplary system 100, for example, to communicateoccupant information. System 100 may take many different forms andinclude multiple and/or alternate components and facilities. While anexemplary system 100 is shown in FIG. 1, the exemplary componentsillustrated in FIG. 1 are not intended to be limiting. Indeed,additional or alternative components and/or implementations may be used.

As illustrated in FIG. 1, system 100 may include a vehicle 101 (e.g.,vehicles 101 a-c), a device 102 (e.g., devices 102 a-d), a device 104(e.g., devices 104 a-b), a device 106 (e.g., devices 106 a-b), afacility 110, a sensor 112, a call center 113, a server 114, a database115, a subscriber network 117, and communication links or connections119. The system 100 may be configured to be utilized by a vehicleoccupant 121 (e.g., occupants 121 a-d). The devices 102, 104, and 106,sensor 112, and server 114 may include a processor 105 and a memory 107.A program 108 may be loaded to the memory 107 and may includeinstructions to be executed by the processor 105. The devices 102, 104,and 106 and sensor 112 may include a transceiver 109 or separatetransmitters and receivers in place of a transceiver 109. The devices102, 104, and 106 may include a user interface 111.

The occupant information may include any information or data associatedwith one or more occupants 121 or vehicle 101. The occupant informationmay be received using the user interface 111, stored as part of memory107 or database 115, communicated between any of devices 102, 104, and106, sensor 112, and server 114 using transceiver 109, and displayed aspart of the user interface 111. The occupant information may includesensor outputs including one or more issues including, for example, oneor more medical issues associated with one or more occupants 121 ofvehicle 101, one or more vehicle issues associated with vehicles 101, ora combination issue including one or more medical issues and one or morevehicle issues, as discussed in further detail below. The occupantinformation may further include location information such as an occupantlocation or vehicle location provided by devices 102 and 104, as alsodiscussed in more detail below. The occupant information may includemedical records of one or more occupants 121, which may be stored aspart of memory 107 or database 115. The occupant information may furtherinclude an occupant history reflecting prior medical issues, vehiclecollisions, vehicle citations (e.g., speeding or parking tickets), andcriminal offenses (e.g., operating while intoxicated or other alcoholrelated offenses), which may be stored as part of memory 107 or database115. Thus, the occupant information transferred between and utilized byany of devices 102, 104, and 106, sensor 112, server 114, and database115.

The system 100 may include an overall network infrastructure throughwhich the devices 102, 104, and 106, sensor 112, server 114, anddatabase 115 may communicate, for example, to transfer occupantinformation between any of devices 102, 104, and 106, sensor 112, server114, and database 115, e.g., using connections 119. For instance, thesystem 100 may generally include edge, distribution, and core devices(e.g., server 114) and enables a path (e.g., connection 119) for theexchange of occupant information between different devices and systems(e.g., between any of devices 102, 104, and 106, sensor 112, server 114,and database 115). In general, a network (e.g., system 100 or subscribernetwork 117) may be a collection of computing devices and other hardwareto provide connections and carry communications.

Further, the system 100 may utilize any networking technology including,for example, any wired or wireless network. The network may include apacket network or any other network having an infrastructure to carrycommunications. Exemplary networks may include one or more of a cellularnetwork, a vehicle-to-vehicle (V2V) communication network, telephonenetwork, global area network, wide area networks (WAN), a VoIP network,an LTE network, a VoLTE (Voice over LTE) network, fiber optic network,cable network, television network, local area networks (e.g., Ethernet),wireless local area networks (e.g., radio-frequency (RF) or Wi-Fi),power-line networks, private networks (e.g., configured to providenetwork access limited to devices having network-specific software), orcombinations thereof. The system 100 is provided as an example, and thuswhile a system 100 is illustrated, this illustration may represent asingle network infrastructure, a combination of different networkscomponents and technologies, and/or a plurality of networks.

Subscriber network 117 may be configured to provide communicationsservices to and between a plurality of devices (e.g., devices 102, 104,and 106 and server 114). The subscriber network 117 may providecommunications services, such as packet-switched network services (e.g.,Internet access, VoIP (Voice over Internet Protocol) communicationservices) and location services (e.g., device positioning), to devicesconnected to the subscriber network 117. Exemplary subscriber network117 may include any network discussed above, for example a cellularnetwork, a telephone network, VoIP network, an LTE network, a VoLTE(Voice over LTE) network, a fiber optic network, or any combinationthereof. Subscriber network 117 may also be configured to generateoccupant information including an occupant location, for example acurrent geographic position of any of devices 102 or 104.

The vehicle 101 may include any vehicle such as any land, air, or watervehicle. Exemplary vehicles 101 a-b may include any passenger or transitvehicle. Further, an exemplary vehicle 101 c may include an emergencyvehicle such as an ambulatory, police, firefighting, or roadsideassistance vehicle. The vehicle 101 may be configured to be selectivelycontrolled by the device 106 with varying levels of driver inputincluding human input, for example, by occupant 121. An exemplaryoccupant 121 may include any person occupying the vehicle 101 such asdriver or passenger. Exemplary human inputs may include, for example,steering with a steering wheel, acceleration with an accelerator pedal,and braking with a brake pedal of the vehicle 101. For example, thehuman inputs may be provided by the occupant 121 to direct the vehicle101 along a route, for example, to the facility 110.

The sensor 112 may include any sensor configured to measure and monitoroccupant information and generate one or a plurality of sensor outputsassociated with one or more occupants 121 or vehicle 101. The sensor 112may also be configured to detect occurrence of and generate sensoroutputs indicating one or more issues including, for example, a medicalissue such as a body disorder associated with one or more occupants 121,a vehicle issue such as a malfunction, damage, or accident associatedwith the vehicle 101, or a combination issue including medical andvehicle issues. The sensor 112 may be configured to communicate, usingthe transceiver 109, the sensor outputs indicating the issue to devices102, 104, and 106 in communication with other devices 102, 104, and 106and server 114.

The sensor 112 may include a body sensor configured to detect andgenerate one or more body sensor outputs in response to a medical issueassociated with one or more occupants 121. The sensor 112 may beconfigured to measure one or more body parameters associated with one ormore occupants 121. The sensor 112 may include any wired or wirelesssensor, for example, any health monitor or any wearable, contact, ornon-contact sensor. The sensor 112 may be unattached, releasablyattached, or permanently attached with respect to the occupant 121 orvehicle 101. An exemplary sensor 112 may include a heart rate monitor,cardiac sensor, blood glucose meter, respirometer, spirometer,respiration sensor, optical sensor, electrocardiogram (EKG), medicalimaging device, medical radar device, pulse oximeter, blood pressuremonitor, body temperature monitor, breathalyzer, chemical sensor, ormoisture sensor. The sensor outputs may include body parameters such asa heart rate, glucose level, respiratory rate, eye response, oxygensaturation, blood pressure, body temperature, blood alcohol content,presence of blood, or a combination thereof. The sensor 112, usingtransceiver 109, may be configured to communicate one or more sensoroutputs (e.g., real-time, near real-time, periodically, or uponoccurrence of the medical issue) to the devices 102 and 104, which maycommunicate occupant information along with the sensor output to otherdevices 102 and 104, devices 106, and server 114.

The sensor 112 may further include a vehicle sensor configured to detectand generate one or more vehicle sensor outputs in response to a vehicleissue associated with the vehicle 101, for example, apart from or incombination with a medical issue of occupant 121. An exemplary sensor112 may include, for example, a vehicle condition sensor such as tirepressure sensor, engine sensor, glass break sensor, or crash sensor. Anexemplary sensor 112 may also include a vehicle environment sensor suchas a motion detector, microphone, or camera that are positioned inside,outside, or otherwise associated with the vehicle 101. For example, thesensor 112 may be configured to detect motion of the occupant 121, noiseor speech from the occupant 121, or a visual image of the occupant 121.The sensor 112, using transceiver 109, may be configured to communicatea sensor output (e.g., real-time, near real-time, periodically, or uponoccurrence of the vehicle issue) to the devices 102, 104, and 106 andserver 114.

A threshold associated with the sensor outputs may be stored as part ofmemory 107 or database 115. The threshold may be utilized by the device102 to determine whether a possible issue is present in the occupant121, vehicle 101, or a combination thereof. The threshold may bepredefined (e.g., by occupant 121) as part of the memory 107 or database115 and may include a threshold number, a threshold sequence, a lowerthreshold, an upper threshold, or a threshold range having lower andupper thresholds. The threshold number may be satisfied by apredetermined number of sensor outputs, e.g., two or more sensor outputsmay satisfy the threshold. Further, the threshold sequence may besatisfied with a vehicle sensor output and a body sensor outputoccurring in a predefined order, within a predefined time period of eachother, or a combination thereof. In addition, the threshold range may besatisfied if the sensor outputs are below the lower threshold, above theupper threshold, or otherwise outside the threshold range. For example,sensor outputs beyond the predefined number of sensor outputs, above thelower threshold, below the upper threshold, or in the threshold rangemay indicate that an issue is present with respect to the occupant 121or vehicle 101. Each of the medical and vehicle issues may each have arespective threshold.

For example, the threshold range for a body parameter such as arespiratory rate may have a lower threshold (e.g., approximately 10-15breaths per minute) and an upper threshold (e.g., approximately 20-25breaths per minute). If the sensor output indicates a respiration rateoutside the threshold range, a medical issue may be present. If thesensor output indicates that the respiration rate is in the thresholdrange, a medical issue is not present with respect to this bodyparameter. If all of the parameters of the sensor outputs are in theirrespective threshold ranges, the device 102 may determine that nomedical issue is present.

As another example, the threshold range for a body parameter such as aheart rate may have a lower threshold (e.g., approximately 20-40 beatsper minute) and an upper threshold (e.g., approximately 180-200 beatsper minute). If the sensor output indicates a heart rate outside thethreshold range, a medical issue may be present. If the sensor outputindicates that the heart rate is in the threshold range, a medical issueis not present with respect to this body parameter. If all of theparameters of the sensor outputs are in their respective thresholdranges, the device 102 may determine that no medical issue is present.

As a further example, the threshold number of sensor outputs may besatisfied when a predefined number of sensor outputs is reached, e.g.,one, two, three, or more sensor outputs. The sensors 112 may include afirst sensor 112 configured to generate a first sensor output, a secondsensor 112 configured to generate a second sensor output, and a thirdsensor 112 configured to generate a third sensor output. If thepredefined number of sensor outputs is two or more, the threshold numberwould be satisfied by any two the first, second, and third sensoroutputs, but not by only one of the first, second, and third sensoroutputs. Thus, a decision tree may be appropriate in the case ofreviewing sensor outputs from a plurality of sensors 112 that is moresophisticated than solely relying on a threshold of a single sensor 112.As a result, satisfaction of the threshold may involve the considerationof multiple sensor outputs, whether from a single sensor 112 over timeor a plurality of sensors 112.

The threshold sequence may be satisfied based on a vehicle sensor outputand a body sensor output occurring in a predefined order, within apredefined time period of each other, or a combination thereof. Thepredefined time period may be any number of seconds or minutes. Forexample, the threshold sequence may be satisfied by a vehicle sensoroutput (e.g., indicating a vehicle crash) followed by and within apredefined time period of a body sensor output (e.g., indicating aninjury resulting from the crash). Alternatively, the threshold sequencemay also be satisfied by a body sensor output (e.g., indicating amedical issue) followed by and within a predefined time period of avehicle sensor output (e.g., indicating a resulting crash).

A comparison of the sensor outputs of two or more sensors 112 may beused to determine an issue type including a medical issue, a vehicleissue, or a combination issue including both. A first sensor 112 (e.g.,a body sensor) may be configured to generate a first sensor output and asecond sensor 112 (e.g., a vehicle sensor) may be configured to generatea second sensor output. In response to the first sensor output, thedevice 102 may determine that the issue type includes a medical issue.In response to the second sensor output, the device 102 may determinethat the issue type includes a vehicle issue. In response to both thefirst and second sensor outputs, the device 102 may determine that theissue type includes a combination issue. Similar to the threshold, adecision tree may be appropriate in the case of reviewing sensor outputsfrom a plurality of sensors 112 that is more sophisticated than solelyrelying on a threshold of a single sensor 112. As a result,determination of the issue type may involve the consideration ofmultiple sensor outputs, whether from a single sensor 112 over time or aplurality of sensors 112.

For example, the sensors 112 may include a moisture sensor configured toprovide a sensor output in response to moisture, a chemical sensorconfigured to provide a sensor output in response to blood, and a crashsensor configured to provide a sensor output in response the vehicle 101impacting another object. In response to blood contacting a moisturesensor and a chemical sensor, the moisture and chemical sensors maygenerate a sensor output indicating a medical issue but no vehicleissue. In response to a beverage contacting the moisture sensor, onlythe moisture sensor may generate a sensor output indicating no medicalor vehicle issue. In response to the vehicle 101 being driven intowater, both the moisture sensor and crash sensor may generate a sensoroutput indicating a vehicle issue but no medical issues. Accordingly,two or more sensors 112 may be utilized to determine the issue type.

The device 102 may include a computing device such as an occupantdevice. The device 102 may be configured to communicate information,e.g., occupant information, with devices 104, device 106, sensor 112,server 114, or other devices 102. An exemplary device 102 may include amobile device, cellular phone, smart-phone, super-phone, tabletcomputer, next generation portable device, handheld computer, notebook,or laptop.

For example, the device 102 a may receive (e.g., using the userinterface 111) occupant information from one or more occupants 121,communicate (e.g., using the transceiver 109) the occupant informationto any of devices 102 b-e and server 114, receive (e.g., using thetransceiver 109) a response from any of devices 102 b-e and server 114,and display (e.g., using the user interface 111) the response to theoccupant 121.

The device 104 may include a computing device such as a telematicsdevice. The device 104 may be configured to communicate information,e.g., occupant information, with other portions of the system 100, e.g.,devices 102 and other devices 104. The telematics device may beconfigured to provide telematics services, for example, using locationinformation (e.g., using a global positioning system (GPS)) and thesubscriber network 117 (e.g., using the transceiver 109). Exemplarytelematics services may include automatic driving assistance, vehicletracking, container tracking, cold storage tracking, fleet management,safety information (e.g., road hazard or weather notifications),emergency warning information (e.g., emergency vehicle notifications),and vehicle status (e.g., a notification of vehicle information orvehicle issues). The device 104 may be configured to access thesubscriber network 117 using the transceiver 109 or by connecting withthe device 102 in communication with the subscriber network 117.

The device 106 may include a computing device such as a vehiclecomputer. The device 106 may be configured to selectively controloperation of the vehicle 101 according to one or more driving modes.Exemplary driving modes may include a driver operated mode (e.g.,operation of the vehicle 101 determined by human input), a partial orsemi-autonomous mode including automated, driver assistance orcorrection (e.g., partial operation of the vehicle 101 by device 106along with human input), or an autonomous or driverless mode (e.g., fulloperation of the vehicle 101 by device 106 without human input). In thedriver operated mode, the device 106 may allow human input to operatethe vehicle 101 and without controlling a route of the vehicle 101. Inthe automated mode, the device 106 may provide automated control of thevehicle 101 (e.g., electronic stability control, automatic braking,adaptive cruise control, or lane keeping) in conjunction with humaninput. The autonomous driving mode may provide control of the vehicle101 without human input or intervention, for example, guiding thevehicle 101 along a route while controlling the steering, acceleration,and braking.

The device 106, e.g., using the processor 105, may be configured totransfer driver inputs of occupant 121 with respect to vehicle controlsof vehicle 101, e.g., between the occupant 121 and device 106 andbetween various body portions of the occupant 121. Exemplary vehiclecontrols may include acceleration, braking, clutch operation, andsteering controls. For example, the occupant 121 may have a medicalissue resulting in inhibited use of one or more first body portions(e.g., arms, hands, legs, or feet) and may wish to transfer vehicleoperation to one or more second body portions (e.g., the other of arms,hands, legs, or feet). The device 102 or 104, e.g., using the userinterface 111, may receive a confirmation (e.g., a verbal, textual, ortactile indication) from the occupant 121 that the medical issue ispresent. The device 102 or 104, e.g., using the transceiver 109, mayinstruct the device 106 to utilize, e.g., the partial or semi-autonomousmode. The device 106, e.g., using the partial or semi-autonomous mode,may then automatically operate one or more first vehicle controls (e.g.,acceleration, braking, or clutch operation control) of the vehicle 101while still allowing the occupant 121 to operate one or more secondvehicle controls (e.g., steering control or other controls typicallyoperated by the inhibited body portions). Alternatively, instead of thevehicle 101 taking over the first vehicle controls, the device 106 maytransfer control of the first vehicle controls to the occupant 121 usingan alternative control mechanism, e.g., a hand-operated controlmechanism such as steering wheel paddle shifters or a turn-signal ordirectional stalk, configured replace the vehicle operationstraditionally performed by another control mechanism. For example, thehand-operated control mechanism may be utilized to provide acceleration,braking, or clutch operation control, thereby replacing a foot-operatedcontrol mechanism. Alternatively, the device 106, e.g., using thepartial or semi-autonomous mode, may change the vehicle operations thatare operated by a particular control mechanism. For example, the device106 may convert a turn-signal or directional signal stalk into anacceleration control. The device 102, 104, or 106, using the processor105, may determine what level of partial, or full, autonomous control toimplement on the vehicle 101, e.g., based on the confirmation fromoccupant 121. The device 106, e.g., using the partial autonomous mode,may be configured to transfer vehicle control between a first controlmechanism (e.g., hand-operated controls) and a second control mechanism(e.g., foot-operated controls), which may be specifically adapted forsuch transferred control of the vehicle 101 between various bodyportions of the occupant 121. Thus, device 106 may be configured totransfer vehicle controls between the occupant 121 and device 106 and,in addition, between various body portions of the occupant 121.

The device 106, e.g., using the processor 105, may be configured toprovide adaptive correction of the driver inputs of the occupant 121 ofvehicle 101, e.g., relative to a baseline profile. The device 106 mayprovide adaptive correction to correct or adjust a driver input, e.g.,in response to a medial issue. The device 106 may be configured tomonitor, e.g., using the sensors 112, and store, e.g., as part of memory107, the driver inputs for vehicle controls (e.g., acceleration,braking, clutch operation, and steering control) and sensor outputs overa setup time period. The device 106 may be configured to generate, e.g.,using the processor 105, and store, e.g., using the memory 107, thebaseline profile including, e.g., average ranges for the driver inputsand sensor outputs. With the baseline profile, the device 106, e.g.,using the processor 105, may be configured to monitor the driver inputsand sensor outputs for a monitoring time interval. The device 106, e.g.,using the processor 105, may be configured to then compare the driverinputs to the baseline profile and compare the sensor outputs to thebaseline profile or to the threshold, as discussed above. If at leastone of the driver inputs and sensor outputs are within the baselineprofile (e.g., a sharp driver input such as acceleration, braking,clutch operation, or steering outside the baseline profile, but anindication that no medial or vehicle issue is present), the device 106may continue to monitor the driver inputs for another monitoringinterval. However, if the driver inputs and sensor outputs are outsidethe baseline profile (e.g., a sharp driver input and an indication of amedial or vehicle issue), the device 106 may notify the occupant 121that the driver inputs and sensor outputs are outside the baselineprofile (e.g., using an audio, textual, or tactile notification or acombination thereof), prompt the occupant 121 to confirm or overrideadaptive correction as discussed in more detail below, and implementadaptive correction thereby adjusting the driver inputs in conformancewith the baseline profile. Thus, the device 106 continue to monitor thedriver inputs and sensor outputs in response to only a sharp driverinput, but device 106 may utilize adaptive correction in response to asharp driver input along with a medical or vehicle issue. Alternatively,even if the driver inputs are within the baseline profile, the device106 may apply adaptive correction in response to a medial or vehicleissue meeting the threshold.

The device 106, e.g. using adaptive correction, may adjust aninput-output ratio between one or more driver inputs and a response ofthe vehicle 101. The device 106, e.g., using the processor 105, mayincrease or decrease a response by the vehicle 101 to the driver inputs,an amount of force from the occupant 121 that is required to operate thevehicle, or an amount of force from the vehicle 101 that is translatedback to the occupant 121. For example, the device 106, e.g., using theprocessor 105, may be configured to adjust the input ratio for steering(e.g., by amplifying or dampening a vibration or steering resistancetranslated to the occupant 121 or a steering response of the vehicle101) or for acceleration (e.g., by amplifying or dampening a throttleresponse of the vehicle 101 by adjusting a fuel injector duty cyclemapping). Further, the device 106, e.g., using the processor 105, maytransfer vehicle controls and utilize the partial or semi-autonomousmode as discussed above, e.g., to adjust the vehicle controls to keepthe vehicle 101 within a particular lane or operate the vehicle 101 to aside or other safe portion of a roadway. Alternatively, the device 106,e.g., using the processor 105, may utilize the autonomous mode tooperate the vehicle to the facility 110, as discussed in further detailbelow.

The processor 105 of devices 102 and 104 and server 114 may beconfigured to determine without human intervention a route between anoccupant location and a facility location or, in the event the vehicle101 is inoperable due to a vehicle issue, a route may be determinedbetween an emergency vehicle location and an occupant location. Theoccupant location of occupant 121 or vehicle 101 a and the emergencyvehicle location of vehicle 101 c may be determined, for example, usingthe GPS of device 102 or 104. The facility location may be determined byaccessing a facility list as part of memory 107 or database 115 or aninternet facility directory. The route may be determined, using theprocessor 105, with one or more maps as part of memory 107, database115, or an internet map directory.

In use, the device 102 or 104 may determine the occupant location usingthe GPS, access the facility list, select a facility 110 based on theoccupant location and facility list using the processor 105 of any ofdevices 102 and 104 or server 114, determine the route to the facilityusing the processor 105 of any of devices 102 and 104 or server 114,provide the determined route to the device 106 using the transceiver109, and direct or operate the vehicle 101 to the facility 110 using thedevice 106. Alternatively, the processor 105 of device 106 may determinethe route and, in addition, direct or operate the vehicle 101 to thefacility 110. The devices 102 and 104 may further communicate anotification including the occupant information (e.g., occupant locationand the medical or vehicle condition) to the other devices 102, 104, and106 and server 114 using the transceiver 109.

The processor 105 may further be configured to determine the route basedin part on a medical severity, stored as part of memory 107 or database115. The medical severity may be associated with one or more occupants121 or vehicles 101. The medical severity may be assigned by theprocessor 105 based in part on the particular medical issues and anumber of occupants 121 affected by medical issues. For example, a firstmedical issue associated with a life threatening condition (e.g., amajor injury or body disorder such as an organ failure) may be assigneda higher medical severity and a second medical issue associated with anon-life threatening condition (e.g., a minor injury or body disordersuch as a bone fracture) may be assigned a lower medical severity.Furthermore, an first occupant 121 or vehicle 101 with a higher numberof medical issues (e.g., multiple injuries or body disorders) may beassigned a higher medical severity and an second occupant 121 or vehicle101 with a lower number of medical issues (e.g., a single injury or bodydisorder) may be assigned a lower medical severity. Thus, the devices102, 104, and 106, sensor 112, and server 114 may determine the routebased in part on the medical severity.

The devices 102 and 104 and server 114 may be configured to selectivelyauthorize the device 106 to utilize the automated and autonomous drivingmodes, for example, based on each of the automated and autonomousdriving mode being permitted by applicable laws, e.g., stored as part ofmemory 107 or database 115, according to the occupant location or inresponse to a medical issue associated with one or more occupants 121.For example, the device 106 may be configured to utilize each of theautomated and autonomous driving modes only when permitted by applicablelaws. Alternatively, in response to a medical issue, the device 106 mayutilize the autonomous driving mode even when prohibited by applicablelaws, because the occupant 121 may be unable to safely drive the vehicle101. Further, in response to a medical issue, devices 102 and 104 andserver 114 may authorize the device 106 to alternatingly flash the rightand left headlights, right and left taillights, and emergency warninglights (e.g., light emitting diodes (LEDs)), and blow the horn of thevehicle 101 a.

The vehicle 101 may include traffic preemption devices that may be usedin conjunction with the devices 102, 104, and 106 and server 114. Thedevices 102 and 104 may authorize the device 106 to utilize the trafficpreemption devices to cause traffic lights along the route of thevehicle 101 to cycle thereby granting right-of-way along the route ofthe vehicle 101. More specifically, the devices 102, 104, and 106 maycommunicate with directly with nearby traffic lights or with server 114,which may be in communication with a computer (e.g., operated by adepartment of transportation) that controls the traffic lights. Inresponse to a medical or vehicle issue, the devices 102, 104, and 106may communicate with the traffic lights or server 114 to change thetraffic signals from green to red along the route of vehicle 101. Thetraffic lights may change in response to the vehicle location determinedusing GPS, e.g., changing from red to green when the vehicle 101approaches the traffic signals and returning to normal operation afterthe vehicle 101 passes the traffic signals.

The devices 102, 104, and 106 may further include a computing devicesuch as a vehicle-to-vehicle (V2V) device, for example between devices106 a-106 b. The V2V device may be configured to providevehicle-to-vehicle (V2V) communication, for example, utilizing anyvehicle-to-vehicle (V2V) communication protocol such as a dedicatedshort-range communications (DSRC) protocol. The V2V device, using thetransceiver 109, may be configured to wirelessly exchange of vehicledata between nearby vehicles, for example, between vehicle 101 a and 101b. The vehicle data may include a position, a speed, and a location of avehicle 101, which may be determined using a global positioning system(GPS). The vehicle data may also indicate that the vehicle 101 isoperating in a driver operation, automated, or autonomous driving mode.The V2V device (e.g., of vehicle 101 a) may be configured to communicatewith one or more other V2V devices (e.g., of vehicle 101 b) to provide anotification upon or associated with entering an intersection, departinga highway, an obstacle, a sudden halt, an accident, a lane change, ornearby ambulances, fire trucks, or police cars. Thus, the devices 102,104, and 106, using V2V communication, may communicate with nearbyvehicles 101.

The devices 102, 104, and 106, sensor 112, and server 114 may beconfigured to communicate, using the transceiver 109, a notificationincluding occupant information between any of devices 102, 104, and 106,sensor 112, and server 114. Exemplary notifications may include, forexample, an automated phone call, short message service (SMS) or textmessage, e-mail, http link, web-based portal, V2V communication, or anyother type of electronic communication. The notification may includeoccupant information, may be communicated between any of devices 102,104, and 106 and server 114 and may be displayed as part of the userinterface 111 of any of devices 102. The notification may be provided toan emergency contact list of the occupant 121, which may be stored aspart of memory 107 or database 115. The notification may include adescription of medical and vehicle issues. For example, the notificationmay additionally incorporate by way of example an automated phone callto a user such as medical, police, firefighting, ambulance, or roadsideassistance personnel or another occupant 121.

In response to a medical or vehicle issue, the devices 102, 104, and106, using the transceiver 109, may be configured to seek help fromother nearby devices 102, 104, and 106. The devices 102, 104, and 106may provide an occupant location to the server 114 and, in response, theserver 114 may send a notification to other devices 102, 104, and 106having location information nearby the occupant location. Thenotification may include a message seeking help along with the medicalor vehicle issue. For example, the notification may be received bynearby medical professionals (e.g., doctors or nurses) using the otherdevices 102, 104, and 106 that may provide aid or protection.

The devices 102 and 104 may be configured to access a facility list. Thefacility list may include a list of facilities 110 based on the locationinformation of device 102 or device 104. The facility list may be storedas part of memory 107 or database 115. The facility list may include afacility location and a capability level associated with each facility110. The facility list may be generated or populated by the occupant121, facility 110, or call center 113 using the user interface 111 ofdevice 102 or using an internet directory accessed using the subscribernetwork 117 in communication with the device 102. The capability levelmay include a trauma center level associated with medical specialistsand equipment available at each facility 110, for example, to treatmedical issues associated with occupants 121. The device 102 or 104 maybe configured to determine (e.g., using the GPS) an occupant location,access (e.g., using the transceiver 109) a facility list based on theoccupant location, select (e.g., using the processor 105) a facility 110from the facility list based on the occupant location and the medicalissue, generate (e.g., using the processor) a route to selected facility110, and provide the route to occupant 121 or device 106, which maydrive the vehicle 101 to the selected facility 110.

The facility 110 may include any healthcare facility or other situationappropriate (e.g., safe) location for occupants 121. An exemplaryfacility 110 may include any facility that offers medical servicesincluding, for example, a hospital, a doctor's office, a nurse-ledclinic, a health clinic, an inpatient care center, an outpatient carecenter, a surgical center, an ambulatory center, an urgent care center,a community health center, a retail clinic, or a free clinic.

The call center 113 may include any call center responsible for a callto an emergency telephone number for emergency services. An exemplarycall center 113 may include a public-safety answering point (PSAP).Exemplary emergency services may include police, firefighting, andambulance services. The call center 113 may also dispatch emergencyservices in response to the call for emergency services. The call center113 may be configured to determine location information associated withthe call by using the subscriber network 117. The call center 113 may beconfigured to send a notification (e.g., an automated phone call) to oneor a plurality of devices 102 to provide an alert in response to themedical or vehicle issue. For example, the call center 113, using thedevice 102 e, may receive a notification from the device 102 aindicating a medical or vehicle issue and, in response, send anotification to devices 102 b-d.

The server 114 may include any computing system, for example, atelematics server. The server 114 may be configured to communicativelyconnect with and transfer occupant information between the devices 102,104, and 106 and database 115. The server 114 may be connected, viaconnection 119, to the devices 102, 104, and 106 and database 115.Server 114 may be in continuous or periodic communication with devices102, 104, and 106. Server 114 may include a local, remote, orcloud-based server or a combination thereof and may be in communicationwith and provide occupant information (e.g., as part of memory 107 ordatabase 115) to any of devices 102, 104, and 106. The server 114 mayfurther provide a web-based user interface (e.g., an internet portal) tobe displayed by any of the user interface 111 of devices 104. The server114 may communicate the occupant information with devices 102 and 104using a notification including, for example automated phone call, shortmessage service (SMS) or text message, e-mail, http link, web-basedportal, or any other type of electronic communication. In addition, theserver 114 may be configured to store occupant information as part ofmemory 107 or database 115. The server 114 may include a single or aplurality of centrally or geographically distributed servers 114. Server114 may be configured to store and coordinate occupant information withdevices 102, 104, and 106 and database 115.

The devices 102, 104, and 106 may be configured to receive and respondto the sensor output of the sensor 112. The device 102, 104, and 106,using the transceiver 109, may receive the sensor output from sensor112, e.g., including an indication of an issue such as a vehicle issue,medical issue, or a combination thereof. In response a sensor outputindicating an issue or after a user-defined time period specified withuser interface 111, the devices 102, 104, and 106 may prompt theoccupant 121 for a confirmation including an indication associated with,for example, if the occupant 121 can safely operate the vehicle 101, ifthe occupant needs medical attention, if the vehicle 101 is operable, orany similar or alternative prompts. The prompt and correspondingconfirmation may be indicated, for example, using any audio, verbal,visual, textual, or tactile indication, button press, sensor output, ora combination thereof. An exemplary confirmation may indicate a “yes” or“no” or any other positive or negative indication. The confirmation mayalso be received by the sensor 112, for example, using a button as partof the sensor 112. Thus, devices 102, 104, and 106 may be configured todetermine the condition of the occupants 121 and vehicle 101.

The devices 102, 104, and 106 may be configured to respond to aconfirmation or lack of confirmation from the occupant 121. If theconfirmation or lack of confirmation indicates that the occupant 121should not be driving or needs medical attention, the device 102 a or104 a may select a facility 110 from the facility list based on thelocation information and the confirmation, instruct the device 106 a todrive the vehicle 101 to the selected facility 110 (e.g., using theautonomous driving mode), and communicate a notification includingoccupant information to the devices 102 b-e and server 114. If theconfirmation or lack of confirmation indicates that the vehicle is notoperable, the devices 102 a-102 b may send a notification to the otherdevices 102 a-104 b and server 114, which may communicate the occupantinformation (e.g., location information and a medical or vehiclecondition) with the vehicle 101 c (e.g., an emergency vehicle).Alternatively, if the confirmation indicates that the occupant 121 isokay to drive or does not need medical attention, the device 102 a or104 a may instruct the vehicle 106 a continue the current driving mode.

The sensor 112, devices 102 and 104, and server 114 may be configured topopulate and maintain a sensor record, as part of the memory 107 ordatabase 115. The sensor record may include the sensor outputs fromsensor 112 and the associated confirmation, as discussed above. Thesensor record may also include a sensor accuracy based on a number offalse positives between the sensor outputs for a particular sensor 112and the confirmation of the occupant 121. For example, if a sensoroutput indicates that the occupant 121 has an unreadable or anabnormally low or high body parameter while the confirmation indicatesthat the occupant 121 is okay, this indicates a false positive.Accordingly, a higher number of false positives results in a lowersensor accuracy as part of the sensor record of memory 107 or database115. Alternatively, a lower number of false positives results in ahigher sensor accuracy as part of the sensor record of memory 107 ordatabase 115. Thus, the devices 102 and 104 and server 114 may utilizethe sensor record to determine the sensor accuracy associated with eachsensor 112.

The processor 105 may be configured to selectively implement the driveroperation, automated, and autonomous driving modes, for example, asselected by the occupant 121 with user interface 111 or according toinstructions from the program 108. The occupant 121 may utilize the userinterface 111 to select between the driver operation, automated, andautonomous driving modes. The occupant 121 may determine this selection,for example, based on whether the occupant 121 can safely operate thevehicle 101, which may be indicated to the occupant 121 by displayingthe sensor outputs indicating a medical or vehicle issue as part of userinterface 111. Further, in response to a medical issue, the occupant 121may utilize the user interface 111 to continue with or select betweenthe driver operation, automated, and autonomous driving modes.Alternatively, in response to a medical issue, the processor 105 mayautomatically switch from the driver operation or automated mode to theautonomous driving mode. Further, if the vehicle 101 is not operable,the transceiver 109 of device 102 a may send the occupant location tothe other devices 102, which may route the vehicle 101 c (e.g., anambulatory vehicle) to the vehicle 101 a.

The devices 102 and 104 and server 114 may be configured to sendoccupant information to the device 102 c of vehicle 101 c, device 102 dof facility 110, and device 102 e of call center 113. For example, afterselecting the facility 110 as discussed above, the occupant information(e.g., medical issues and medical records) may be sent to the selectedfacility 110 using the transceiver 109 of the devices 102 and 104 orserver 114. Further, one or more facilities 110, using the transceiver109 of device 102 d, may send occupant information (e.g., medicalrecords for each of occupants 121) to the vehicle 101 c. The server 114or device 102 d, using the processor 105, may coordinate the arrival ofoccupants 121 at the selected facility 110 and their respective occupantinformation (e.g., medical records) and present, using the userinterface 111, the occupant information to medical personnel of thevehicle 101 c (e.g., while traveling toward or upon arrival at vehicle101 a) or the selected facility 110 (e.g., upon arrival or duringcheck-in). The medical personnel may review the occupant information,which may include sensor outputs and medical records. For example, thedevice 102 d may be configured to provide a diagnosis of one or moreoccupants 121 remotely based on the sensor outputs and medical records,e.g., while the vehicle is in route to the facility 110. Based on theoccupant information, the device 102 d may be configured to expeditecheck-in of the occupant 121 at facility 110, route the occupant 121 toan area of the facility 110 associated with a medical issue of theoccupant 121, and facilitate the preparation of equipment at thefacility 110 associated with the medical issue.

Furthermore, the devices 102 and 104 and server 114 may be configured toapply a medical severity to a plurality of vehicles 101 (e.g., vehicles101 a and 101 b) or occupants 121 (e.g., occupants 121 a-d). Forinstance, an accident may involve a plurality of vehicles 101 andoccupants 121. The processor 105 may evaluate the occupant information(e.g., the sensor outputs and medical records) from each of theoccupants 121. The processor 105 may triage or prioritize the occupants121 based on the medical severity, compare the medical severity and themedical capability of each facility 110, and select a facility from afacility list based on the comparison and the occupant location. Forexample, each facility 110 (e.g., a hospital) may be configured to, orhave the capability to, accommodate a predefined number of patients,which may, or may not be, an absolute maximum. Thus, the server 114 mayroute one or more vehicles 101 to the facility 110 having a closerfacility location to the occupant location until the facility reachesthe predefined number of patients it can accommodate. After thepredefined number is met, the server 114 may route vehicles to thefacility 110 having the next closest facility location to the occupantlocation. Further, the vehicles 101 with occupants 121 having a highermedical severity may be routed to a facility 110 having the closerfacility location or having a higher medical capability, even if thevehicle 101 has occupants 121 with a lower medical severity. Othervehicles 101 with occupants 121 having a lower medical severity may berouted to a facility 110 having a further facility location or a lowermedical capability.

The user interface 111 of devices 102, 104, and 106 may include adisplay or a mechanism to connect to a display, support user interfaces,and/or communicate occupant information within the system 100. The userinterface 111 may include any input or output device to facilitate thereceipt or presentation of information (e.g., occupant information) inaudio, visual or tactile form or a combination thereof. Examples of adisplay may include, without limitation, a touchscreen, a vehicledashboard, cathode ray tube display, light-emitting diode display,electroluminescent display, electronic paper, plasma display panel,liquid crystal display, high-performance addressing display, thin-filmtransistor display, organic light-emitting diode display,surface-conduction electron-emitter display, laser TV, carbon nanotubes,quantum dot display, interferometric modulator display, and the like.The display may present user interfaces to any user of devices 102, 104,and 106, for example, one or more occupants 121 or any medical, police,firefighting, ambulance, or roadside assistance personnel.

The transceiver 109 (e.g., of devices 102, 104, and 106 and sensor 112)may communicatively connect the devices of system 100, for example,using any type of wired or wireless network connection. The transceiver109 may include a single transceiver or a combination of transmittersand receivers. The wireless network may utilize a wireless transmitter(e.g., cellular, radiofrequency (RF) or Wi-Fi transmitter) oftransceiver 109. Transceiver 109 may be configured to communicativelyconnect any or all of devices 102, 104, and 106, sensor 112, and server114. Transceiver 109 may be used for digital or analog signal transfers.For instance, transceiver 109 may include any antenna technologyincluding cellular, V2V communication, radiofrequency (RF), near fieldcommunication (NFC), Bluetooth®, Wi-Fi, or the like. Transceiver 109 mayinclude any technology that implements a wireless exchange of occupantinformation by converting propagating electromagnetic waves to and fromconducted electrical signals. Transceiver 109 may include any technologythat is used to exchange occupant information wirelessly using radiowaves over a radio range or network that enables communication.

The devices 102, 104, and 106 may include a location determinationtechnology that enables the determination of location information (e.g.,a current geographic position) of any of devices 102, 104, and 106.Examples of location determination technology may include, withoutlimitation, global positioning systems (GPS), indoor positioning system,local positioning system, and mobile phone tracking. The devices 102,104, and 106 may be configured to provide a current geographic positionof any of devices 102, 104, and 106, for example, to provide an occupantlocation of occupant 121, a vehicle location of vehicle 101, or afacility location of facility 110.

The connections 119 may be any wired or wireless connections between twoor more endpoints (e.g., devices or systems), for example, to facilitatetransfer of occupant information (e.g., including subscriber informationand occupant information). Connection 119 may include a wirelessconnection, for example, to communicatively connect the devices 102,104, and 106 with subscriber network 117. Connection 119 may include aV2V connection, for example, to communicatively connect device 106 awith device 106 b. Connection 119 may include a wide area networkconnection, for example, to communicatively connect server 114 withsubscriber network 117. Connection 119 may include a radiofrequency(RF), near field communication (NFC), Bluetooth®, Wi-Fi, or a wiredconnection, for example to communicatively connect the devices 102 a-b,104 a-b, and 106 a-b.

Any portion of system 100, e.g., devices 102, 104, and 106 and server114, may include a computing system and/or device that includes aprocessor 105 and a memory 107. Computing systems and/or devicesgenerally include computer-executable instructions, where theinstructions may be executable by one or more devices such as thoselisted below. Computer-executable instructions may be compiled orinterpreted from computer programs created using a variety ofprogramming languages and/or technologies, including, withoutlimitation, and either alone or in combination, Java™, C, C++, VisualBasic, Java Script, Perl, SQL, PL/SQL, Shell Scripts, etc. The system100, e.g., devices 102, 104, and 106 and server 114 may take manydifferent forms and include multiple and/or alternate components andfacilities, as illustrated in the Figures further described below. Whileexemplary systems, devices, modules, and sub-modules are shown in theFigures, the exemplary components illustrated in the Figures are notintended to be limiting. Indeed, additional or alternative componentsand/or implementations may be used, and thus the above communicationoperation examples should not be construed as limiting.

In general, computing systems and/or devices (e.g., devices 102, 104,and 106 and server 114) may employ any of a number of computer operatingsystems, including, but by no means limited to, versions and/orvarieties of the Microsoft Windows® operating system, the Unix operatingsystem (e.g., the Solaris® operating system distributed by OracleCorporation of Redwood Shores, Calif.), the AIX UNIX operating systemdistributed by International Business Machines of Armonk, N.Y., theLinux operating system, the Mac OS X and iOS operating systemsdistributed by Apple Inc. of Cupertino, Calif., the BlackBerry OSdistributed by Research In Motion of Waterloo, Canada, and the Androidoperating system developed by the Open Handset Alliance. Examples ofcomputing systems and/or devices such as devices 102, 104, and 106 andserver 114 may include, without limitation, mobile devices, cellularphones, smart-phones, super-phones, tablet computers, next generationportable devices, mobile printers, handheld computers, notebooks,laptops, secure voice communication equipment, networking hardware,computer workstations, or any other computing system and/or device.

Further, processors such as processor 105 receive instructions frommemories such as memory 107 or database 115 and execute theinstructions, thereby performing one or more processes, including one ormore of the processes described herein. Such instructions and otheroccupant information may be stored and transmitted using a variety ofcomputer-readable mediums (e.g., memory 107 or database 115). Processorssuch as processor 105 may include any computer hardware or combinationof computer hardware that is configured to accomplish the purpose of thedevices, systems, and processes described herein. For example, theprocessor 105 may be any one of, but not limited to single, dual,triple, or quad core processors (on one single chip), graphicsprocessing units, visual processing units, and virtual processors.

A memories such as memory 107 or database 115 may include, in general,any computer-readable medium (also referred to as a processor-readablemedium) that may include any non-transitory (e.g., tangible) medium thatparticipates in providing occupant information or instructions that maybe read by a computer (e.g., by the processors 105 of the devices 102,104, and 106 and server 114). Such a medium may take many forms,including, but not limited to, non-volatile media and volatile media.Non-volatile media may include, for example, optical or magnetic disksand other persistent memory. Volatile media may include, for example,dynamic random access memory (DRAM), which typically constitutes a mainmemory. Such instructions may be transmitted by one or more transmissionmedia, including radio waves, metal wire, fiber optics, and the like,including the wires that comprise a system bus coupled to a processor ofa computer. Common forms of computer-readable media include, forexample, a floppy disk, a flexible disk, hard disk, magnetic tape, anyother magnetic medium, a CD-ROM, DVD, any other optical medium, punchcards, paper tape, any other physical medium with patterns of holes, aRAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip orcartridge, or any other medium from which a computer can read.

The devices 102, 104, and 106 and server 114 may include processor 105that is configured to perform operations with respect to the occupantinformation, for example update and store occupant information as partof memory 107 or database 115. The devices 102, 104, and 106 and server114 may further utilize the processor 105 to transfer and displayoccupant information, as described herein.

Further, databases, data repositories or other occupant informationstores (e.g., memory 107 and database 115) described herein maygenerally include various kinds of mechanisms for storing, providing,accessing, and retrieving various kinds of occupant information,including a hierarchical database, a set of files in a file system, anapplication database in a proprietary format, a relational databasemanagement system (RDBMS), etc. Each such occupant information store maygenerally be included within (e.g., memory 107) or external (e.g.,database 115) to a computing system and/or device (e.g., devices 102,104, and 106 and server 114) employing a computer operating system suchas one of those mentioned above, and/or accessed via a network (e.g.,system 100 or subscriber network 117) or connection in any one or moreof a variety of manners. A file system may be accessible from a computeroperating system, and may include files stored in various formats. AnRDBMS generally employs the Structured Query Language (SQL) in additionto a language for creating, storing, editing, and executing storedprocedures, such as the PL/SQL language mentioned above.

FIG. 2 illustrates an exemplary diagnostic process 200. Process 200 maytake many different forms and include multiple and/or alternatecomponents and facilities. While an exemplary process 200 is shown inFIG. 2, the exemplary components illustrated in FIG. 2 are not intendedto be limiting. Indeed, additional or alternative components and/orimplementations may be used.

At block 202, the device 102 may monitor one or more sensor outputs fromone or a plurality of sensors 112, e.g., vehicle sensors, body sensors,or a combination thereof. Moreover, as noted above, inputs from aplurality of different sensors 112 may be agglomerated. For example, theone or more sensor outputs may be associated with a possible issue,e.g., a medical issue associated with occupant 121 from a body sensoroutput from a body sensor, a vehicle issue associated with the vehicle101 from a vehicle sensor output from a vehicle sensor, or a combinationissue including both medical and vehicle issues from body and vehiclesensors.

At decision point 204, the device 102, using the processor 105, maydetermine if the sensor outputs from the one or a plurality of sensors112 indicate a possible issue. If the sensor outputs are not associatedwith a possible issue, the device 102 may continue to monitor sensoroutputs. If the sensor outputs are associated with a possible issue, thedevice 102 may determine if the sensor outputs satisfy a threshold.

At decision point 206, the device 102, using the processor 105, maydetermine if the sensor outputs satisfy the threshold. The threshold mayinclude a threshold number, a threshold sequence, a lower threshold, anupper threshold, or a threshold range, as discussed above. If multiplesensors 112 are being used, the combined output of the sensors 112 mayresult in the determination of an issue even if the output from any onesensor by itself may not confirm such an issue. The device 102 maygenerate the determination in response to two or more sensor outputsconfirming the issue. For example, a first sensor (e.g., a moisturesensor) may generate a first sensor output in response to a spilleddrink, which may not meet the threshold. However, if a first sensor(e.g., a moisture sensor) and a second sensor (e.g., a chemical sensor)generate respective first and second sensor outputs in response to abody fluid, the threshold may be satisfied. As a further example, thethreshold may be satisfied by a vehicle sensor output and a body sensoroutput occurring within a predefined time period, e.g., indicating avehicle crash and resulting injuries, as discussed above. Thus, adecision tree may be appropriate in the case of reviewing data from aplurality of sensors 112 that is more sophisticated than solely relyingon the threshold range of a single sensor 112. As a result, theexemplary step recognizes that the threshold determination may involvethe consideration of multiple sensor outputs, whether from a singlesensor over time or a plurality of sensors.

If the threshold is not satisfied, the device 102 may continue tomonitor sensor outputs. If the threshold is satisfied, the device 102may prompt for a confirmation from occupant 121 to verify the sensoroutputs (e.g., to verify the possible issue).

At block 208, the device 102 may prompt the occupant 121 for aconfirmation to verify the sensor outputs (e.g., to verify the possibleissue) using the user interface 111.

At decision point 210, the device 102 may determine if the confirmationverifies the sensor output, e.g., thereby verifying the issue. Forexample, the occupant 121 may verbally indicate that there is no issue,which is inconsistent with the sensor output thereby failing to verifythe issue. Alternatively, the occupant 121 may verbally indicate thatthere is an issue (e.g., a medical issue, a vehicle issue, or acombination issue) or may be silent (e.g., indicating incapacitation dueto a medical issue or a combination issue), thereby confirming thesensor output. If the confirmation and sensor output are inconsistent,the device 102 may store a false positive associated with the sensoroutput and continue to monitor the sensor outputs. If the confirmationand sensor output are consistent thereby verifying the issue, the device102 may determine if the vehicle is inoperable.

At block 212, if the confirmation indicates that the medical issue isnot present, device 102 may instruct device 106 to allow the vehicle 101to continue in the current driving mode and store a false positiveassociated with the issue as part of the memory 107 or database 115.Alternatively, the processor 105 may determine that a medical conditionexists based on a lack of confirmation at block 212.

At decision point 214, the device 102 may determine the issue typeincluding, for example, a medical issue, a vehicle issue, or acombination issue. For example, the type of issue may be used todetermine if medical treatment based on a medical issue, if the vehicle101 is inoperable thereby requiring roadside assistance based on avehicle issue, or a combination issue requiring both. For example, thedevice 102 may check the sensor outputs to determine if vehicle andmedical issues are present. If the sensor outputs include a vehicleissue, then the device 102 may determine that the vehicle 101 a is notinoperable and send a notification to dispatch vehicle 101 c (e.g.,roadside assistance) to vehicle 101 a. If the sensor outputs include acombination issue, then the device 102 may determine that the vehicle101 a is not inoperable and send a notification to dispatch vehicle 101c (e.g., roadside assistance and an ambulance) to vehicle 101 a. If thesensor outputs include a medical issue but not a vehicle issue, then thedevice 102 may determine that the vehicle 101 a is inoperable, send anotification to the facility 110, and drive the vehicle 101 to facility110 in the autonomous driving mode.

At block 216, the device 102 may send a notification to dispatch vehicle101 c (e.g., an emergency vehicle) to vehicle 101 a and continue tomonitor the sensor outputs.

At block 218, if the confirmation indicates that the medical issue ispresent, instruct the device 106 to operate the vehicle 101 using thesemi-autonomous or autonomous driving mode, e.g., to drive the vehicle101 to facility 110, and send a notification including the confirmedmedical issue to the facility 110 using the transceiver 109. Forexample, the notification may allow the facility 110 to prepare for thearrival of the occupant 121, as discussed above. After block 212, thedevice 102 may continue to monitor the sensor outputs.

FIG. 3 illustrates an exemplary routing process 300. Process 300 maytake many different forms and include multiple and/or alternatecomponents and facilities. While an exemplary process 300 is shown inFIG. 3, the exemplary components illustrated in FIG. 3 are not intendedto be limiting. Indeed, additional or alternative components and/orimplementations may be used.

At block 302, the device 102 or 104, using the transceiver 109, orserver 114 may receive a sensor output indicating a medical issueassociated with an occupant 121 of a vehicle from the sensor 112.

At block 304, the device 102 or 104, e.g., using the GPS, may determinean occupant location.

At block 306, the device 102 or 104, using the transceiver 109, or theserver 114 may access or receive a facility list, as part of the memory107 or database 115, having medical capabilities and facility locationsassociated with a plurality of facilities 110.

At block 308, the processor 105 of device 102 or 104 or server 114 mayselect a facility 110 from the facility list based on a comparisonbetween the medical issue and the medical capabilities of the pluralityof facilities 110.

At block 310, if the confirmation indicates a medical issue, the device102 or 104, using the transceiver 109, may instruct the device 106 tooperate the vehicle 101 using an autonomous driving mode, or partial orsemi-autonomous mode, and, in addition, the device 102 or 104 may send,using the transceiver 109, a notification including the confirmedmedical issue to another device 102 or server 114 using the transceiver109.

At block 312, if the confirmation or lack of confirmation indicates nomedical issue, the device 102 or 104, using the transceiver 109, mayinstruct the device 106 allow the vehicle 101 to continue in a currentdriving mode and, in addition, the device 102 or 104 may store, as partof the memory 107 or database 115, a false positive associated with thesensor 112. After block 312, the process 300 ends.

With regard to the processes, systems, methods, heuristics, etc.described herein, it should be understood that, although the steps ofsuch processes, etc. have been described as occurring according to acertain ordered sequence, such processes could be practiced with thedescribed steps performed in an order other than the order describedherein. It further should be understood that certain steps could beperformed simultaneously, that other steps could be added, or thatcertain steps described herein could be omitted. In other words, thedescriptions of processes herein are provided for the purpose ofillustrating certain embodiments, and should in no way be construed soas to limit the claims.

FIG. 4 illustrates an exemplary adaptive correction process 400. Process400 may take many different forms and include multiple and/or alternatecomponents and facilities. While an exemplary process 400 is shown inFIG. 4, the exemplary components illustrated in FIG. 4 are not intendedto be limiting. Indeed, additional or alternative components and/orimplementations may be used.

At block 402, the sensor 112 may monitor driver inputs and sensoroutputs for a setup period, as discussed above.

At block 404, the device 102 or 104, e.g., using the processor 105, maygenerate and store a baseline profile, e.g., as part of memory 107.

At block 406, the device 102 or 104, e.g., using the processor 105, maymonitor the driver inputs and sensor outputs for a monitoring interval.

At decision point 408, the device 102 or 104, e.g., using the processor105, determine if the driver inputs are in the baseline profile. If thedriver inputs are in the baseline profile, the processor may continue tomonitor the driver inputs and sensor outputs. If the driver inputs arenot in the baseline profile, the processor 105 may determine if thesensor outputs are in a threshold, as discussed above.

At decision point 410, the device 102 or 104, e.g., using the processor105, may determine if the sensor outputs are in the threshold. If thesensor outputs are in the threshold, the processor 105 may store a falsepositive, e.g., as part of memory 107. If the sensor outputs are not inthe threshold, the processor 105 may provide a notification.

At block 412, the device 102 or 104, e.g., using the processor 105, maystore a false positive, e.g., as part of memory 107.

At block 414, the device 102 or 104, e.g., using the processor 105, mayprovide a notification, e.g., to another device 102 or 104 or server114, confirm or override adaptive correction, as discussed above.

At block 416, the device 102 or 104, e.g., using the processor 105, mayprovide prompt occupant 121 to confirm or override adaptive correction,as discussed above.

At decision point 418, the device 102 or 104, e.g., using the userinterface 111, may receive a confirmation to accept or override ofadaptive correction. If the confirmation indicates that adaptivecorrection is accepted or no response is received, the device 102 or 104may instruct device 106 to utilize adaptive correction. If theconfirmation indicates that adaptive correction is overridden, thedevice 106 may continue using the current driving mode.

At block 420, the device 106, e.g., using the processor 105, maycontinue using the current driving mode.

At block 422, the device 102 or 104, e.g., using the transceiver 109,may instruct the device 106 to utilize adaptive correction, e.g., in thesemi-autonomous driving mode.

After block 422, the process 400 restarts at block 406.

Accordingly, it is to be understood that the above description isintended to be illustrative and not restrictive. Many embodiments andapplications other than the examples provided would be apparent uponreading the above description. The scope should be determined, not withreference to the above description, but should instead be determinedwith reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled. It is anticipated andintended that future developments will occur in the technologiesdiscussed herein, and that the disclosed systems and methods will beincorporated into such future embodiments. In sum, it should beunderstood that the application is capable of modification andvariation.

All terms used in the claims are intended to be given their broadestreasonable constructions and their ordinary meanings as understood bythose knowledgeable in the technologies described herein unless anexplicit indication to the contrary in made herein. In particular, useof the singular articles such as “a,” “the,” “said,” etc. should be readto recite one or more of the indicated elements unless a claim recitesan explicit limitation to the contrary.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A system comprising: a user interface; aprocessor and a memory having a program communicatively connected to theprocessor, the processor being configured to: receive a body sensoroutput associated with an occupant of a vehicle; receive a vehiclesensor output associated with the vehicle; compare, using the processor,at least one of the body and vehicle sensor outputs with a threshold;prompt, using the user interface, for a confirmation associated with atleast one of the body and vehicle sensor outputs; determine, using theprocessor, an issue type based on at least one of the body and vehiclesensor outputs; send a notification including the issue type; receive afacility list having a medical capability and a facility location for aplurality of facilities; select, using the processor, one of theplurality of facilities from the facility list based in part on acomparison between the medical issue and the medical capability of atleast a portion of the plurality of facilities; and determine, using theprocessor, a route to the selected one of the plurality of facility. 2.The system of claim 1, wherein the issue type includes a medical issueassociated with the occupant.
 3. The system of claim 2, wherein theissue type further includes a vehicle issue associated with the vehicle.4. The system of claim 1, the processor further being configured toinstruct a vehicle computer of the vehicle to change from a currentdriving mode to an autonomous driving mode.
 5. The system of claim 1,the processor further being configured to instruct a vehicle computer ofthe vehicle to drive the vehicle to the selected facility based on thedetermined route.
 6. The system of claim 1, wherein the notificationincludes the issue type and is sent to at least one of a facility and anemergency vehicle.
 7. A non-transitory computer-readable medium tangiblyembodying computer-executable instructions of a program being executableby a processor of a computing device to provide operations comprising:receive a body sensor output associated with an occupant of a vehicle;receive a vehicle sensor output associated with the vehicle; compare,using the processor, the body and vehicle sensor outputs with athreshold; prompt, using the user interface, for a confirmationassociated with the body and vehicle sensor outputs; determine, usingthe processor, an issue type based on the body and vehicle sensoroutputs; send a notification including the issue type; receive afacility list having a medical capability and a facility location for aplurality of facilities; select one of the plurality of facilities fromthe facility list based in part on a comparison between the medicalissue and the medical capability of at least a portion of the pluralityof facilities; and determine a route to the selected one of theplurality of facilities.
 8. The medium of claim 7, wherein the issuetype includes a medical issue associated with the occupant.
 9. Themedium of claim 8, wherein the issue type further includes a vehicleissue associated with the vehicle.
 10. The medium of claim 7, theoperations further comprising instruct a vehicle computer of the vehicleto change from a current driving mode to an autonomous driving mode. 11.The medium of claim 7, the operations further comprising instruct avehicle computer of the vehicle to drive the vehicle to the selectedfacility based on the determined route.
 12. The medium of claim 7,wherein the notification includes the issue type and is sent to at leastone of a facility and an emergency vehicle.
 13. A method comprising:receiving a body sensor output associated with an occupant of a vehicle;receiving a vehicle sensor output associated with the vehicle;comparing, by way of a processor, at least one of the vehicle and bodysensor outputs with a threshold; prompting, by way of a user interface,for a confirmation associated with the at least one of the body andvehicle sensor outputs; determining, by way of the processor, an issuetype based on at least one of the body and vehicle sensor outputs;sending a notification including the issue type; receiving a facilitylist having a medical capability and a facility location for a pluralityof facilities; selecting, using a processor, one of the plurality offacilities from the facility list based in part on a comparison betweenthe medical issue and the medical capability of at least a portion ofthe plurality of facilities; and determining, without humanintervention, a route to the selected one of the plurality offacilities.
 14. The method of claim 13, wherein the issue type includesa medical issue associated with the occupant.
 15. The method of claim14, wherein the issue type further includes a vehicle issue associatedwith the vehicle.
 16. The method of claim 13, the method furthercomprising instructing the vehicle to change from a current driving modeto an autonomous driving mode.
 17. The method of claim 13, the methodfurther comprising instructing a vehicle computer of the vehicle todrive the vehicle to the selected facility based on the determinedroute.